Report the task directives referenced by the task script - #7505

✅ Deploy Preview for nextflow-docs canceled.

Thanks for putting this together — I like the direction, and I agree the valRefs reuse is a much lighter mechanism than what I had in #7483.

Pros over #7483, as I see it:

• Two lines of production change in the core, vs. a new AST collector, a Closure subclass, and a BodyDef constructor arg.
• Works with the v1 parser for free — nextflow.ast.VariableVisitor already collects full property chains, so this actually removes a v1/v2 inconsistency rather than adding machinery.
• The no-hash-impact argument holds: TaskConfig#setContext puts task in the context holder, so getGlobalVars skips every task.* as a local var, and getTaskExtensionDirectiveVars re-adds only task.ext.*.
• Doesn't touch config compilation or closure rendering, which is your main objection to Disable resource prediction for processes referencing task.memory #7483 and a fair one.

Blocker: no config coverage. This shape is common in nf-core/configs institutional profiles:

process {
    clusterOptions = { "-l h_vmem=${task.memory.toString().replaceAll(/[\sB]/, '')}" }
}

clusterOptions itself is grid-only and never reaches the Seqera path, so this exact line is harmless — but it shows the pattern is standard practice, not hypothetical. The same shape on a command-affecting directive does reach us:

process { withName: FOO { ext.args = { "-Xmx${task.memory.toGiga()}g" } } }

Here the script only shows task.ext.args; the closure is resolved by LazyMap, never by the template engine, so getVariableNames() can't see it. And config closures carry no source at runtime — ClosureToStringVisitor only runs under renderClosureAsString, and TaskClosure is only applied to when/stub. So there's nothing to inspect at submit time; this needs a compile-time hook.

Two smaller things: the stub isn't actually covered — TaskContext.variableNames comes from processor.getTaskBody().getValNames(), and the stub is a separate TaskClosure whose refs are never collected. And matching the whole task. namespace means isDirectiveReferenced('workDir') answers for a non-directive; #7483 filtered against DirectiveDsl for that reason.

I'm attempting to cover the config reference extending this PR.

I have another option that we can try. Let me submit another PR

Have you actually encountered the ext.args example in a real pipeline?

#7506 applies a fix at the runtime layer by simply recording accesses to task properties. That way we don't have to play whack-a-mole in the compiler

The main config concern as pattern like this

process {
    clusterOptions = { "-l h_vmem=${task.memory.toString().replaceAll(/[\sB]/, '')}" }
}

there are plenty in nf-core/configs

Comparing the five approaches against the requirement: detect task.memory in script/shell/template and config, direct or via closure.

One fact collapses the matrix: a config value cannot reference task unless it is a closure. ext.args = "-Xmx${task.memory}g" fails at parse time — v2 raises ConfigParseException, v1 degrades task.memory to an empty ConfigObject and throws MissingMethodException: No signature of method: groovy.util.ConfigObject.toGiga(). So "direct reference in config" is not a case to cover.

#7506 is the one I'd take. Observing the reads rather than inferring them gets the config ext.args case for free — no compiler hook, no Closure subclass, no hash exposure, and it works on both parsers. I checked the funnel claim holds: getMemory() → getMemory0() → get('memory'), getProperty falls through to get(), and the nested ext map is re-resolved on every read (only TaskConfig caches, and the read is recorded before the cache check), so the closure is genuinely re-entered during the window.

Its one gap is the one it already documents: beforeScript/afterScript are resolved by BashWrapperBuilder after the window closes. That looks fixable by widening the recording window over the wrapper build, rather than by adding a parser.

Two results from trying the alternatives:

• Detect task directive references in dynamic config values #7507 reaches full coverage but costs ~900 lines and is v2-config-parser only. It does show Disable resource prediction for processes referencing task.memory #7483's ClosureToStringVisitor patch is avoidable: skip the wrapping when renderClosureAsString is set, since the rendering and running paths are mutually exclusive.
• Disable resource prediction for processes with dynamic command directives #7508 — the no-compiler heuristic ("is any command-affecting directive a closure") — is not viable. Measured on real conf/modules.config: atacseq trips 40/70 processes, rnaseq 20/77, sarek 7/13. The driver is not ext.args (2–6 per pipeline) but ext.prefix = { "${meta.id}.sorted" }, which cannot reference memory. Closing it.

One thing to carry into whichever lands: scope by source directive. clusterOptions = { "-l h_vmem=${task.memory...}" } is standard in nf-core institutional configs and never reaches the Seqera path, so #7483 as written would disable prediction pipeline-wide on it. #7506 sidesteps this for free, since it only observes what the command actually reads.

But nf-core/configs will never apply to SIC because they are for other compute environments

The ext.args example might be a problem if you can find actual usages. Otherwise it's not worth chasing, since we are just applying a quick fix now and a long-term solution later.

But if you want to be extra sure then I would just go with #7506 . It should cover everything: script, config, v1/v2 parser

Just saw your analysis. #7506 works for me. Feel free to test it / clean it up / merge it 👍

Cool, took your advice. Closing this in favour of #7506